Skip to content

Fix pin bump CI handler not triggering on workflow_run#19090

Open
JacobSzwejbka wants to merge 1 commit into
mainfrom
pinbump-cron
Open

Fix pin bump CI handler not triggering on workflow_run#19090
JacobSzwejbka wants to merge 1 commit into
mainfrom
pinbump-cron

Conversation

@JacobSzwejbka
Copy link
Copy Markdown
Contributor

@JacobSzwejbka JacobSzwejbka commented Apr 23, 2026

Summary

  • Fall back to looking up PR by branch name when workflow_run.pull_requests is empty (known GitHub API limitation for cross-workflow triggers)
  • Handle cancelled trunk conclusion alongside failure, which occurs when docker-builds fails and downstream Linux jobs can't start

This PR was authored with help from Claude.

Test plan

  • Verify CI handler triggers correctly on next automated pin bump PR
  • Confirm cancelled trunk runs now trigger fix attempts instead of being silently skipped

@JacobSzwejbka
Fix pin bump CI handler not triggering on PR #19048
a12c059 
Two bugs: workflow_run.pull_requests was empty (known GitHub API
limitation), so fall back to looking up the PR by branch name.
Also handle cancelled trunk conclusion, which happens when
docker-builds fails and Linux jobs can't start.

This PR was authored with help from Claude.
@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Apr 23, 2026 •
edited
Loading

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/19090

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

❌ 3 New Failures, 1 Cancelled Job, 1 Unrelated Failure

As of commit a12c059 with merge base 2d995bc (image):

NEW FAILURES - The following jobs have failed:

CANCELLED JOB - The following job was cancelled. Please retry:

BROKEN TRUNK - The following job failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Apr 23, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 23, 2026

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@JacobSzwejbka